-
-
Notifications
You must be signed in to change notification settings - Fork 414
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[16.0][MIG] account_payment_term_partner_holiday: Migration to 16.0 #744
base: 16.0
Are you sure you want to change the base?
[16.0][MIG] account_payment_term_partner_holiday: Migration to 16.0 #744
Conversation
PabloCatalinaCastello
commented
Jul 2, 2024
•
edited
Loading
edited
- Reopen [16.0][MIG] account_payment_term_partner_holiday #636
8fbceee
to
a9f86cb
Compare
"""Inject a context for getting the partner when computing payment term.""" | ||
for move in self: | ||
super( | ||
AccountMove, self.with_context(move_partner_id=move.partner_id.id) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If self is being iterated the super should be done for "move.with_context(..." not "self.with_context(..."
dcb282e
to
423671b
Compare
Hi @pedrobaeza , could you please take a look at this PR when you have a chance? Thanks! |
Sorry, not using this module. /ocabot migration account_payment_term_partner_holiday |
Sorry for being curious, but can I ask why? Is it just a coincidence, or is there another reason? Thanks Pedro! |
We don't have customers with this need for now. I also personally think that a payment debt shouldn't be delayed because the debtor is on holidays. It's the payer problem. If you go on holiday, program the payments. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
This PR has the |
LGTM! |
There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. |
When you have a client that generates invoices for temporary cycles to their customers, they have to take into account those vacation days to generate the due dates when they are sure that they will be attended. LGTM! |